Greptile Summary

This PR introduces a messaging.queue.depth gauge to the queue server's telemetry, recorded once at worker start and again after every processed message when the consumer also implements Publisher::getQueueSize(). A dedicated test file exercises the three key paths using lightweight in-process stubs so no external broker is needed.

• src/Queue/Server.php: setTelemetry() now creates the gauge; the new private recordQueueDepth() guards on instanceof Publisher, calls getQueueSize(), and records the result with messaging.destination.name / messaging.destination.namespace attributes.
• tests/Queue/E2E/Adapter/ServerTelemetryTest.php: Covers the publisher path (depth recorded), the non-publisher path (skipped), and the failure path (silently swallowed, no values recorded).

Confidence Score: 5/5

Safe to merge — the change is additive, guarded by an interface check, and does not alter any existing message-processing behavior.

The gauge is always initialized (constructor calls setTelemetry(new NoTelemetry())) so no uninitialized-property risk exists. The instanceof Publisher guard ensures nothing changes for consumers that do not support getQueueSize(). The finally-block placement means queue depth is captured after every message without interfering with the success/error callback flow. All three behavioral paths are covered by the new test.

No files require special attention.

Important Files Changed

_{Reviews (3): Last reviewed commit: "Simplify queue depth error telemetry" | Re-trigger Greptile}